Remove Symfony Command Hook After Execution #2492
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #2427
This PR should have been included with #2436
TL;DR of the issue:
The current implementation of the command hooks adds a hook to a
<scope>::run
if it wasn't already added. This could, theoretically, lead to multiple hooks added when considering numerous inheritors.About the fix: Considering that in the previous version the hook was made on
Symfony\Component\Console\Command\Command::__construct
, it means that$scope
fundamentally represents aSymfony\Component\Console\Command\Command
instance. From this, the new implementation directly hooksSymfony\Component\Console\Command\Command::run
instead of adding a seemingly unnecessary intermediary step.Reviewer checklist